Skip to content

Node.js 24.3.0 and 22.17.0#23

Merged
N6REJ merged 4 commits intomainfrom
24.3.0-22.17.0
Jul 4, 2025
Merged

Node.js 24.3.0 and 22.17.0#23
N6REJ merged 4 commits intomainfrom
24.3.0-22.17.0

Conversation

@jwaisner
Copy link
Contributor

@jwaisner jwaisner commented Jul 2, 2025

PR Type

Enhancement


Description

  • Add Node.js versions 24.3.0 and 22.17.0 support

  • Create configuration files and launch scripts

  • Update release properties with download URLs

  • Add npm configuration for new versions


Changes diagram

flowchart LR
  A["New Node.js Versions"] --> B["24.3.0 Configuration"]
  A --> C["22.17.0 Configuration"]
  B --> D["Launch Scripts"]
  C --> D
  B --> E["NPM Configuration"]
  C --> E
  F["Release Properties"] --> G["Download URLs"]
Loading

Changes walkthrough 📝

Relevant files
Enhancement
2 files
launch.bat
Add Node.js 22.17.0 Windows launch script                               
+12/-0   
launch.bat
Add Node.js 24.3.0 Windows launch script                                 
+12/-0   
Configuration changes
14 files
bearsampp.conf
Add Node.js 22.17.0 configuration file                                     
+8/-0     
npmrc
Add npm configuration for Node.js 22.17.0                               
+4/-0     
npmrc.ber
Add npm backup configuration for 22.17.0                                 
+4/-0     
npmrc
Add npm prefix configuration for 22.17.0                                 
+1/-0     
npmrc.ber
Add npm prefix backup for 22.17.0                                               
+1/-0     
npmrc
Add npm prefix configuration for 23.11.0                                 
+1/-0     
npmrc.ber
Add npm prefix backup for 23.11.0                                               
+1/-0     
bearsampp.conf
Add Node.js 24.3.0 configuration file                                       
+8/-0     
npmrc
Add npm configuration for Node.js 24.3.0                                 
+4/-0     
npmrc.ber
Add npm backup configuration for 24.3.0                                   
+4/-0     
npmrc
Add npm prefix configuration for 24.3.0                                   
+1/-0     
npmrc.ber
Add npm prefix backup for 24.3.0                                                 
+1/-0     
build.properties
Update bundle release version to 2025.7.2                               
+1/-1     
releases.properties
Add download URLs for new versions                                             
+2/-0     

Need help?
  • Type /help how to ... in the comments thread for any questions about Qodo Merge usage.
  • Check out the documentation for more information.
  • @jwaisner jwaisner requested a review from N6REJ as a code owner July 2, 2025 21:58
    @jwaisner jwaisner added the enhancement ✨ Improve program label Jul 2, 2025
    @qodo-code-review
    Copy link
    Contributor

    qodo-code-review bot commented Jul 2, 2025

    PR Reviewer Guide 🔍

    (Review updated until commit ed7b26f)

    Here are some key observations to aid the review process:

    ⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪
    🧪 No relevant tests
    🔒 No security concerns identified
    ⚡ Recommended focus areas for review

    Missing Validation

    The batch script lacks error handling and validation for critical operations like file existence checks and command execution failures. The script assumes all paths and commands will work correctly without verification.

    ECHO prefix = %BEARSAMPP_NODEJS_PATH%>%BEARSAMPP_NODEJS_CONFIG_PATH%
    
    "%BEARSAMPP_NODEJS_PATH%\nodevars.bat" & "%BEARSAMPP_NODEJS_PATH%\npm" config set globalconfig "%BEARSAMPP_NODEJS_CONFIG_PATH%" --global
    Version Mismatch

    The release URL for version 23.11.0 contains a date mismatch - the URL shows 2025.3.2 while the release date in the URL path is 2025.4.19, which could indicate an incorrect or outdated URL.

    23.11.0 = https://github.com/Bearsampp/module-nodejs/releases/download/2025.4.19/bearsampp-nodejs-23.11.0-2025.3.2.7z
    24.3.0 = https://github.com/Bearsampp/module-nodejs/releases/download/2025.7.2/bearsampp-nodejs-24.3.0-2025.7.2.7z

    @qodo-code-review
    Copy link
    Contributor

    qodo-code-review bot commented Jul 2, 2025

    PR Code Suggestions ✨

    Latest suggestions up to ed7b26f

    Explore these optional code suggestions:

    CategorySuggestion                                                                                                                                    Impact
    General
    Improve command chaining error handling

    The command chaining with & may fail silently if the first command fails. Use &&
    to ensure the second command only runs if the first succeeds, providing better
    error handling.

    bin/nodejs22.17.0/launch.bat [10]

    -"%BEARSAMPP_NODEJS_PATH%\nodevars.bat" & "%BEARSAMPP_NODEJS_PATH%\npm" config set globalconfig "%BEARSAMPP_NODEJS_CONFIG_PATH%" --global
    +"%BEARSAMPP_NODEJS_PATH%\nodevars.bat" && "%BEARSAMPP_NODEJS_PATH%\npm" config set globalconfig "%BEARSAMPP_NODEJS_CONFIG_PATH%" --global
    • Apply / Chat
    Suggestion importance[1-10]: 7

    __

    Why: The suggestion correctly identifies that using && for command chaining improves script robustness by preventing the second command from running if the first one fails.

    Medium
    • More

    Previous suggestions

    Suggestions up to commit 70dea37
    CategorySuggestion                                                                                                                                    Impact
    Possible issue
    Fix command chaining logic

    The command chaining with & may fail silently if the first command fails. Use &&
    to ensure the second command only runs if the first succeeds, preventing
    configuration corruption.

    bin/nodejs22.17.0/launch.bat [10]

    -"%BEARSAMPP_NODEJS_PATH%\nodevars.bat" & "%BEARSAMPP_NODEJS_PATH%\npm" config set globalconfig "%BEARSAMPP_NODEJS_CONFIG_PATH%" --global
    +"%BEARSAMPP_NODEJS_PATH%\nodevars.bat" && "%BEARSAMPP_NODEJS_PATH%\npm" config set globalconfig "%BEARSAMPP_NODEJS_CONFIG_PATH%" --global
    Suggestion importance[1-10]: 8

    __

    Why: This is a valid correctness fix; using && ensures the npm command only runs if nodevars.bat succeeds, making the script more robust and preventing potential configuration errors.

    Medium
    Suggestions up to commit b3a9d97
    CategorySuggestion                                                                                                                                    Impact
    Possible issue
    Use conditional command chaining

    The command chaining with & may fail silently if the first command fails. Use &&
    to ensure the second command only runs if the first succeeds, preventing
    configuration corruption.

    bin/nodejs22.17.0/launch.bat [10]

    -"%BEARSAMPP_NODEJS_PATH%\nodevars.bat" & "%BEARSAMPP_NODEJS_PATH%\npm" config set globalconfig "%BEARSAMPP_NODEJS_CONFIG_PATH%" --global
    +"%BEARSAMPP_NODEJS_PATH%\nodevars.bat" && "%BEARSAMPP_NODEJS_PATH%\npm" config set globalconfig "%BEARSAMPP_NODEJS_CONFIG_PATH%" --global
    Suggestion importance[1-10]: 7

    __

    Why: The suggestion correctly identifies that using && instead of & improves the script's robustness by preventing the second command from running if the first one fails.

    Medium

    @N6REJ N6REJ merged commit 8745437 into main Jul 4, 2025
    @N6REJ N6REJ deleted the 24.3.0-22.17.0 branch July 4, 2025 12:20
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

    Labels

    enhancement ✨ Improve program

    Projects

    None yet

    Development

    Successfully merging this pull request may close these issues.

    2 participants